Triple
T5767163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L3 |
E127242
|
entity |
| Predicate | partOfFacility |
P66281
|
FINISHED |
| Object | LEP experimental program |
—
|
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: LEP experimental program | Statement: [L3, partOfFacility, LEP experimental program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfFacility Context triple: [L3, partOfFacility, LEP experimental program]
-
A.
associatedSpaceFacility
Indicates that there is a relationship linking an entity to a specific space-related facility with which it is connected or involved.
-
B.
facility
Indicates that one entity is a building, installation, or physical infrastructure used to host, support, or enable the operations or activities of another entity.
-
C.
basedOnFacility
Indicates that something is determined, derived, or decided according to the characteristics, rules, or conditions of a particular facility.
-
D.
partOfTerminalComplex
Indicates that an entity functions as a component or subunit within a larger terminal complex structure.
-
E.
isWithinFacility
Indicates that one entity is physically located inside the boundaries or premises of a specified facility.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02ac9603481909e3fa295d7904a15 |
completed | March 22, 2026, 5:45 p.m. |
Created at: March 22, 2026, 3:49 p.m.