Triple
T25426234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALAC |
E637122
|
entity |
| Predicate | specificationPublished |
P20314
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ALAC, specificationPublished, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specificationPublished Context triple: [ALAC, specificationPublished, true]
-
A.
openSpecificationPublishedBy
Indicates that an open specification has been formally published or issued by a particular entity.
-
B.
specificationStatus
Indicates the current approval or completion state of a specification within its lifecycle (e.g., draft, under review, finalized).
-
C.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
D.
isPublished
chosen
Indicates that an item has been formally made available to the public through some publishing process.
-
E.
publishedEdition
Indicates that one entity is a specific edition or version that has been formally published of another work or resource.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bfdb748190abfd40ed1838d9aa |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:57 p.m.