Triple
T37874446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rite of Exile system |
E944681
|
entity |
| Predicate | requiresCoordination |
P435
|
FINISHED |
| Object | multiple clans |
—
|
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: multiple clans | Statement: [Rite of Exile system, requiresCoordination, multiple clans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCoordination Context triple: [Rite of Exile system, requiresCoordination, multiple clans]
-
A.
coordinatedWithin
Indicates that one entity’s actions, processes, or states are organized and aligned in time or structure within the scope or framework defined by another entity.
-
B.
coordinatedUnder
Indicates that one entity is organized, directed, or managed under the authority or coordination of another entity.
-
C.
coordinatedWith
chosen
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
D.
realmCoordination
Indicates a relationship where multiple realms, domains, or jurisdictions are organized or managed to work together in a coordinated manner.
-
E.
mayCoordinate
Indicates that one entity is permitted or has the option to coordinate or work jointly with another entity.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4:19 p.m.