Triple
T25063523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rdf:Bag |
E627723
|
entity |
| Predicate | statusInRDF11 |
P160841
|
FINISHED |
| Object | legacy container construct |
—
|
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: legacy container construct | Statement: [rdf:Bag, statusInRDF11, legacy container construct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInRDF11 Context triple: [rdf:Bag, statusInRDF11, legacy container construct]
-
A.
ontologyStatus
Indicates the current state or condition of an entity within an ontology lifecycle (e.g., proposed, active, deprecated, or obsolete).
-
B.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
C.
standardizationStatus
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
D.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
-
E.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f60ac643108190ae81561267155791 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f606c15af88190958856a9e467b826 |
completed | May 2, 2026, 2:14 p.m. |
Created at: April 18, 2026, 6:10 a.m.