Triple
T30350097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaldea Security Organization |
E771967
|
entity |
| Predicate | coreSystem |
P110510
|
FINISHED |
| Object | CHALDEAS miniature Earth model |
—
|
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: CHALDEAS miniature Earth model | Statement: [Chaldea Security Organization, coreSystem, CHALDEAS miniature Earth model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreSystem Context triple: [Chaldea Security Organization, coreSystem, CHALDEAS miniature Earth model]
-
A.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
B.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
-
C.
core
chosen
Indicates a central, most important, or foundational part of something in relation to its surrounding or supporting elements.
-
D.
coversSystem
Indicates that one entity provides coverage, applicability, or protection for a particular system.
-
E.
packageSystem
Indicates a relationship where an item or component is organized, bundled, or managed within a particular packaging or distribution 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6820b4b8c81908f5bbae956565ec0 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.