Triple
T30743984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Sun hereditary ruler |
E782767
|
entity |
| Predicate | subordinateClasses |
P170086
|
FINISHED |
| Object | nobles |
—
|
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: nobles | Statement: [Great Sun hereditary ruler, subordinateClasses, nobles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subordinateClasses Context triple: [Great Sun hereditary ruler, subordinateClasses, nobles]
-
A.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
B.
subordinatePositions
Indicates that one position or role is hierarchically lower than and reports to another position or role.
-
C.
subordinateSpecies
Indicates that one species is hierarchically or functionally subordinate to another species within a defined biological or ecological context.
-
D.
subdividedBy
Indicates that something is divided into smaller parts or sections by another entity or criterion.
-
E.
hasMultipleSubclasses
Indicates that a class or category is related to more than one distinct subclass within a hierarchy.
- F. None of above. chosen
Provenance (4 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f6b835c8190b52471f03ebf3453 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68848ad348190a2fb6e841dcfdb7d |
completed | May 2, 2026, 11:27 p.m. |
Created at: April 29, 2026, 8:38 p.m.