Triple
T28023664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organizational Unit |
E707752
|
entity |
| Predicate | cannotSpan |
P168094
|
FINISHED |
| Object | multiple domains |
—
|
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: multiple domains | Statement: [Organizational Unit, cannotSpan, multiple domains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotSpan Context triple: [Organizational Unit, cannotSpan, multiple domains]
-
A.
cannotExceed
Indicates that one quantity, value, or limit must not be greater than another specified quantity or threshold.
-
B.
cannotBeCrossedBy
Indicates that one entity forms a barrier or obstacle that another entity is unable to pass through or traverse.
-
C.
cannotTarget
Indicates that one entity is unable or not permitted to select or act upon another entity as a target.
-
D.
cannotRestrict
Indicates that one entity lacks the authority, ability, or right to impose limits, constraints, or prohibitions on another entity or its actions.
-
E.
cannotBelongTo
Indicates that one entity is not allowed or not able to be a member, part, or element of another entity or group.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 27, 2026, 8:11 p.m.