Triple
T32062146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADIF |
E818772
|
entity |
| Predicate | headerPosition |
P93020
|
FINISHED |
| Object | at beginning of file |
—
|
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: at beginning of file | Statement: [ADIF, headerPosition, at beginning of file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headerPosition Context triple: [ADIF, headerPosition, at beginning of file]
-
A.
header
chosen
Indicates that one entity serves as a heading or title section that precedes and organizes the content of another entity.
-
B.
headLocation
Indicates the spatial position or place where an entity’s head is located.
-
C.
positionHead
Indicates that one entity serves as the head or primary governing element in the positional or syntactic structure of another entity.
-
D.
headFrom
Indicates a relationship where one entity originates, leads, or directs movement or action from another entity as its starting point or source.
-
E.
titleHolderStartPosition
Indicates the position in a sequence or ranking at which an entity begins holding a particular title.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f638908190957f64096c07535f |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:22 a.m.