Triple
T28515251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan constitution |
E721595
|
entity |
| Predicate | traditionalLawgiver |
P88212
|
FINISHED |
| Object | Lycurgus of Sparta |
—
|
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: Lycurgus of Sparta | Statement: [Spartan constitution, traditionalLawgiver, Lycurgus of Sparta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalLawgiver Context triple: [Spartan constitution, traditionalLawgiver, Lycurgus of Sparta]
-
A.
traditionalLawGivingSite
Indicates a location that is traditionally recognized as the place where laws or legal codes were formally given or proclaimed.
-
B.
hadLawgiver
chosen
Indicates that an entity had a specific individual or group who established or codified its laws.
-
C.
customaryLaw
Indicates that a relationship, behavior, or rule is governed by unwritten, traditional norms and practices recognized as binding within a community or group.
-
D.
legalTraditionsTaught
Indicates that one entity teaches, covers, or includes specific legal traditions in its instruction or curriculum.
-
E.
traditionalRule
Indicates that an entity follows, embodies, or is governed by a customary or long-established rule or norm.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 28, 2026, 3:16 a.m.