Triple
T29480876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartiates |
E747781
|
entity |
| Predicate | legalCodeAssociation |
P90195
|
FINISHED |
| Object | Lycurgan reforms |
—
|
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: Lycurgan reforms | Statement: [Spartiates, legalCodeAssociation, Lycurgan reforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalCodeAssociation Context triple: [Spartiates, legalCodeAssociation, Lycurgan reforms]
-
A.
legalCodeName
Indicates that one entity is the official legal code designation or name assigned to another entity within a legal or regulatory system.
-
B.
legalCodeType
Indicates the specific category or classification of a legal code that applies to an entity or situation.
-
C.
legalCodeAppliesTo
chosen
Indicates that a particular legal code or statute is applicable to, or governs, a specified subject, situation, or entity.
-
D.
legalCodeAvailableAt
Indicates that a particular legal code or statute can be accessed, obtained, or consulted at a specified source or location.
-
E.
legalCodeAlternativeName
Indicates that a legal code has an alternative name or designation by which it may also be known.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 28, 2026, 4:03 p.m.