Triple
T10771707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moldanubian Zone |
E254095
|
entity |
| Predicate | structuralComplexity |
P28756
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Moldanubian Zone, structuralComplexity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralComplexity Context triple: [Moldanubian Zone, structuralComplexity, high]
-
A.
hasComplexity
chosen
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
B.
typicalComplexity
Indicates the usual or characteristic level of complexity associated with an entity, process, or situation.
-
C.
spaceComplexity
Indicates the relationship between an algorithm and the amount of memory it requires as a function of input size.
-
D.
hasReasoningComplexity
Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
-
E.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7329a281081909cdc4b971cf69207 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.