Triple
T5281761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C Recommendation Track |
E119513
|
entity |
| Predicate | initialStage |
P63847
|
FINISHED |
| Object | Working Draft |
—
|
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: Working Draft | Statement: [W3C Recommendation Track, initialStage, Working Draft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialStage Context triple: [W3C Recommendation Track, initialStage, Working Draft]
-
A.
firstStageType
Indicates that one entity is the type or category of the first stage or initial phase associated with another entity.
-
B.
firstStageName
Indicates that one entity is the initial or earliest stage name associated with another entity in a sequence or lifecycle.
-
C.
firstStageDescription
Indicates that the value provides a textual explanation or summary of the initial or earliest stage in a multi-stage process or sequence.
-
D.
firstStageEngine
Indicates that an engine functions as the primary propulsion unit used in the first stage of a multi-stage launch vehicle or rocket.
-
E.
firstStageHost
Indicates that an entity serves as the initial host in a multi-stage process or lifecycle involving 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd8c9b82ac819080e798713c0bb4d8 |
completed | March 20, 2026, 6:06 p.m. |
Created at: March 20, 2026, 1:52 p.m.