Triple
T34684923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of God’s House |
E890716
|
entity |
| Predicate | sharesPurposeWith |
P201920
|
FINISHED |
| Object | other leagues of the Three Leagues |
—
|
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: other leagues of the Three Leagues | Statement: [League of God’s House, sharesPurposeWith, other leagues of the Three Leagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPurposeWith Context triple: [League of God’s House, sharesPurposeWith, other leagues of the Three Leagues]
-
A.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesDefinitionWith
Indicates that two entities have the same or an equivalent definition.
-
D.
sharesHomeWith
Indicates that two entities live in the same home or residence.
-
E.
sharesServicesWith
Indicates that two entities make use of, provide, or are connected through the same services or service infrastructure.
- F. None of above. chosen
Provenance (4 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_6a0031ec758c81908a3877bc19ce2701 |
completed | May 10, 2026, 7:21 a.m. |
Created at: May 1, 2026, 2:05 a.m.