Triple
T12315975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 3132 |
E293599
|
entity |
| Predicate | hasInternalStructure |
P22287
|
FINISHED |
| Object | complex |
—
|
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: complex | Statement: [NGC 3132, hasInternalStructure, complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternalStructure Context triple: [NGC 3132, hasInternalStructure, complex]
-
A.
internalStructure
chosen
Indicates that one entity is a component, part, or substructure contained within the overall structure of another entity.
-
B.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
C.
hasRealStructure
Indicates that an abstract object or system is endowed with a concrete, well-defined mathematical or physical structure that makes it realizable or interpretable in a real-world or formal model.
-
D.
hasStructureCount
Indicates the number of structures associated with or contained by a given entity.
-
E.
hasExtendedStructure
Indicates that an entity possesses an additional or elongated structural component beyond its basic or standard form.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.