Triple
T19602533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unidad Especial de Intervención |
E470514
|
entity |
| Predicate | isFullTimeUnit |
P136438
|
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: [Unidad Especial de Intervención, isFullTimeUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFullTimeUnit Context triple: [Unidad Especial de Intervención, isFullTimeUnit, true]
-
A.
mayBeCompletedPartTimeIn
Indicates that an activity, program, or task can be undertaken and finished on a part-time basis within the specified context or location.
-
B.
isOnlyUnitOf
Indicates that one entity is the single, exclusive unit or instance fulfilling a particular role, function, or type in relation to another entity.
-
C.
isUnitIn
Indicates that a specific unit is located within or belongs to a particular container, group, or context.
-
D.
eligibilityUnit
Indicates that one entity serves as the unit or basis used to determine another entity’s eligibility for a benefit, status, or condition.
-
E.
isRelatedUnit
Indicates that one unit has a defined relationship or association with another unit within a given system or context.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64080a57c8190837cbe82b93163bf |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.