Triple
T31439759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thousand-Year Door chamber |
E802033
|
entity |
| Predicate | developerContext |
P83649
|
FINISHED |
| Object | Intelligent Systems |
—
|
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: Intelligent Systems | Statement: [Thousand-Year Door chamber, developerContext, Intelligent Systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerContext Context triple: [Thousand-Year Door chamber, developerContext, Intelligent Systems]
-
A.
developerStudio
chosen
Indicates that a software developer or development team is associated with, works at, or uses a particular development studio or integrated development environment (IDE).
-
B.
platformDeveloper
Indicates that one entity is the developer or creator responsible for building or maintaining the other entity as a platform.
-
C.
developmentArc
Indicates the progression and transformation of something over time, typically outlining key stages of growth, change, or maturation within a broader narrative or process.
-
D.
developerRenamedTo
Indicates that a developer previously known by one name is now identified by a new name.
-
E.
developmentPillar
Indicates that one entity serves as a fundamental pillar or core focus area supporting the development or growth of another entity.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 30, 2026, 9:04 p.m.