Triple
T23387511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PUA-A |
E593923
|
entity |
| Predicate | hasBlockStatus |
P152046
|
FINISHED |
| Object | allocated but unassigned |
—
|
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: allocated but unassigned | Statement: [PUA-A, hasBlockStatus, allocated but unassigned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBlockStatus Context triple: [PUA-A, hasBlockStatus, allocated but unassigned]
-
A.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
B.
hasBroadcastStatus
Indicates the current broadcast-related state or condition of an item, such as whether it is scheduled, live, completed, or unavailable.
-
C.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
D.
hasGroupStatus
Indicates that an entity possesses a particular status, role, or condition within a group or collective context.
-
E.
hasUnitStatus
Indicates that an entity is associated with a particular operational or condition status as a unit.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a498fd08819085e90a872d9d0c7a |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:35 p.m.