Triple
T29430123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hexamilion wall |
E746403
|
entity |
| Predicate | defensiveLineType |
P175670
|
FINISHED |
| Object | land wall |
—
|
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: land wall | Statement: [Hexamilion wall, defensiveLineType, land wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveLineType Context triple: [Hexamilion wall, defensiveLineType, land wall]
-
A.
defensiveLineCharacteristic
Indicates a characteristic or attribute that describes the nature, style, or qualities of a defensive line in a competitive or strategic context.
-
B.
primaryDefensiveLine
Indicates the main line of defense that first engages or protects against an opposing force or threat.
-
C.
defensiveTackle
Indicates that an entity plays the defensive tackle position, typically lining up on the interior of the defensive line to disrupt offensive plays.
-
D.
usedDefensiveLine
Indicates that an entity employed or deployed a particular defensive line as part of its strategy or actions.
-
E.
opponentDefensiveLine
Indicates the defensive line formed by the opposing side in a competitive or adversarial context.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 28, 2026, 3:12 p.m.