Triple
T27582507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4918 |
E699617
|
entity |
| Predicate | definesHeader |
P179201
|
FINISHED |
| Object | Depth |
—
|
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: Depth | Statement: [RFC 4918, definesHeader, Depth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesHeader Context triple: [RFC 4918, definesHeader, Depth]
-
A.
definesTable
Indicates that one entity specifies or establishes the structure, schema, or identity of a table used by another entity.
-
B.
definesBody
Indicates that one entity specifies or determines the physical structure, form, or composition of another entity’s body.
-
C.
sectionDefines
Indicates that a specific section formally specifies, describes, or establishes the meaning, rules, or scope of another element or concept.
-
D.
definesElement
Indicates that one entity specifies or determines the nature, structure, or identity of another entity as its defining element.
-
E.
definesFlag
Indicates that one entity specifies or establishes a particular flag or boolean indicator used by another entity or process.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 27, 2026, 2:03 p.m.