Triple
T9453632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OGLE-II |
E227958
|
entity |
| Predicate | usesFilter |
P88263
|
FINISHED |
| Object | I-band |
—
|
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: I-band | Statement: [OGLE-II, usesFilter, I-band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFilter Context triple: [OGLE-II, usesFilter, I-band]
-
A.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
B.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
C.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
D.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
usesProfile
Indicates that one entity employs, operates under, or is associated with a particular profile in performing its actions or functions.
- 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_69ca8439f8bc8190997f2ef40c9f0bc2 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f8c7b3481909c1182b41d8c27a9 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:52 p.m.