Triple
T27984888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maronite monasteries |
E706716
|
entity |
| Predicate | includesCommunitiesOf |
P8617
|
FINISHED |
| Object | monks |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: monks | Statement: [Maronite monasteries, includesCommunitiesOf, monks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCommunitiesOf Context triple: [Maronite monasteries, includesCommunitiesOf, monks]
-
A.
includesCommunitiesFrom
Indicates that one entity encompasses or contains communities that originate from or belong to another entity.
-
B.
includesInSomeCommunities
Indicates that an entity is considered a member or part of certain, but not necessarily all, communities.
-
C.
includesCommunity
chosen
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
-
D.
servedCommunitiesIncluding
Indicates that an entity provided services or benefits to a set of communities that includes, but may not be limited to, the specified communities.
-
E.
associatedCommunity
Indicates a relationship where an entity is linked or connected to a particular community with which it is involved or identified.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 27, 2026, 7:47 p.m.