Triple
T3600576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan army |
E76243
|
entity |
| Predicate | enforcedValue |
P50153
|
FINISHED |
| Object | collective over individual |
—
|
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: collective over individual | Statement: [Spartan army, enforcedValue, collective over individual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcedValue Context triple: [Spartan army, enforcedValue, collective over individual]
-
A.
enforcedOn
Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
-
B.
originallyEnforcedBy
Indicates that a rule, law, policy, or agreement was first implemented and upheld by a particular enforcing authority or agent.
-
C.
enforcedLaw
Indicates that an authority actively applies or upholds a specific law to regulate behavior or resolve situations.
-
D.
enforcedInRegion
Indicates that a rule, policy, or condition is actively applied and upheld within a specified geographic or administrative region.
-
E.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1a1e8c48190a28ea3ddfe8c4e54 |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9261a948190b67f6c6ac0dae2e9 |
completed | March 8, 2026, 6 p.m. |
Created at: March 8, 2026, 3:22 p.m.