Triple
T34634122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sagamihara |
E889366
|
entity |
| Predicate | hasJAXAFacility |
P179720
|
FINISHED |
| Object | Sagamihara Campus of ISAS |
—
|
NE NERFINISHED |
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: Sagamihara Campus of ISAS | Statement: [Sagamihara, hasJAXAFacility, Sagamihara Campus of ISAS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJAXAFacility Context triple: [Sagamihara, hasJAXAFacility, Sagamihara Campus of ISAS]
-
A.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasJCR
Indicates that one entity possesses, is associated with, or is linked to a specific JCR (Journal Citation Reports) value, record, or classification.
-
C.
hasFacadeBy
Indicates that one entity’s façade (front-facing exterior surface) is designed, created, or provided by another entity.
-
D.
hasFacadeSystem
Indicates that one entity possesses or is equipped with a particular façade system as part of its structure or design.
-
E.
hasFacilityFunction
Indicates that a facility performs, supports, or is designated for a particular function or operational role.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:04 a.m.