Triple
T35050827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitespring Bunker |
E1011324
|
entity |
| Predicate | hasResidentAI |
P48031
|
FINISHED |
| Object | MODUS |
E2123496
|
NE 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: MODUS | Statement: [Whitespring Bunker, hasResidentAI, MODUS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentAI Context triple: [Whitespring Bunker, hasResidentAI, MODUS]
-
A.
hasAI
chosen
Indicates that one entity possesses, incorporates, or is equipped with an artificial intelligence system.
-
B.
hasRasa
Indicates that one entity possesses, exhibits, or is characterized by a particular emotional flavor, aesthetic sentiment, or expressive quality (rasa) associated with another entity.
-
C.
hasTypicalResident
Indicates that an entity characteristically or commonly has a particular type of resident associated with it.
-
D.
hasResidentAdvisers
Indicates that a place, institution, or housing unit is assigned one or more resident advisers responsible for supporting and overseeing its residents.
-
E.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
- F. None of above.
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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37cfe198fc81909bea21d760c5a0f7 |
completed | June 21, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.