Triple
T29572132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvian dynasty |
E753341
|
entity |
| Predicate | saidToRule |
P63550
|
FINISHED |
| Object | Alba Longa |
—
|
NE NERFINISHED |
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: Alba Longa | Statement: [Silvian dynasty, saidToRule, Alba Longa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saidToRule Context triple: [Silvian dynasty, saidToRule, Alba Longa]
-
A.
assumedRuleOf
chosen
Indicates that one entity is presumed or taken to hold authoritative control, governance, or dominion over another entity, typically without definitive confirmation.
-
B.
saidBy
Indicates that a particular statement, quote, or utterance was spoken or produced by a specific entity.
-
C.
ruled in
Indicates that an authority, such as a court or judge, has made a formal decision or judgment in favor of a particular party or position.
-
D.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
E.
laysDownRulingOn
Indicates that an authority formally issues or establishes a decision, judgment, or rule concerning a particular matter or case.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d47de5481908e4f3ae9fae613c3 |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 5:59 p.m.