Triple
T14280569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan war party |
E354033
|
entity |
| Predicate | supportedUseOf |
P15794
|
FINISHED |
| Object | Spartan hoplite army |
—
|
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: Spartan hoplite army | Statement: [Spartan war party, supportedUseOf, Spartan hoplite army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedUseOf Context triple: [Spartan war party, supportedUseOf, Spartan hoplite army]
-
A.
supportsUse
chosen
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
B.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
-
C.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
D.
supportedAfter
Indicates that one entity provided support to another only after a specified event, time, or condition had occurred.
-
E.
supportedRight
Indicates that one entity endorsed, upheld, or actively backed the right or entitlement held by another entity.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697b5e8081908e5b91a3a1c55df9 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.