Triple
T25201839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobius Digital |
E631142
|
entity |
| Predicate | knownForDesignApproach |
P102320
|
FINISHED |
| Object | environmental storytelling |
—
|
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: environmental storytelling | Statement: [Mobius Digital, knownForDesignApproach, environmental storytelling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForDesignApproach Context triple: [Mobius Digital, knownForDesignApproach, environmental storytelling]
-
A.
documentsDesignApproachOf
Indicates that one entity records or specifies the design approach used for another entity.
-
B.
designMethod
Indicates that one entity is used as the method, approach, or technique by which another entity is designed or created.
-
C.
knownForPerspective
chosen
Indicates that an entity is recognized or notable for a particular viewpoint, angle, or way of seeing or interpreting something.
-
D.
knownForDecision
Indicates that an entity is recognized or notable specifically for making a particular decision.
-
E.
roadDesignApproach
Indicates the method or strategy used to plan, configure, or engineer the design of a road or roadway system.
- F. None of above.
Provenance (3 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 12:51 p.m.