Triple
T33212125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REXIS |
E850188
|
entity |
| Predicate | isStudentBuilt |
P176193
|
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: [REXIS, isStudentBuilt, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStudentBuilt Context triple: [REXIS, isStudentBuilt, true]
-
A.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
B.
wasBuilt
Indicates that one entity constructed, created, or assembled another entity, typically at a specific time or over a period.
-
C.
isBuilding
Indicates that an entity functions as or is classified as a building.
-
D.
builtWithout
Indicates that something was constructed or created in the absence of a particular component, material, tool, or condition.
-
E.
builtThrough
Indicates that something was created, developed, or achieved by means of a specified method, process, or intermediary.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:30 a.m.