Triple
T33752629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château Rauzan-Gassies |
E864886
|
entity |
| Predicate | classificationRank |
P10762
|
FINISHED |
| Object | Second Growth |
E1972878
|
NE 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: Second Growth | Statement: [Château Rauzan-Gassies, classificationRank, Second Growth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationRank Context triple: [Château Rauzan-Gassies, classificationRank, Second Growth]
-
A.
taxonRank
Indicates the formal hierarchical rank (such as species, genus, family, etc.) that a given taxon occupies within a biological classification system.
-
B.
rankingCategory
chosen
Indicates the classification or type of ranking under which an entity is evaluated or ordered.
-
C.
classRank
Indicates the relative academic standing or position of an entity within a class or cohort based on performance or criteria.
-
D.
establishedTaxonomicRank
Indicates that one entity has formally defined or assigned the taxonomic rank or classification level of another entity within a biological taxonomy.
-
E.
formationRank
Indicates the hierarchical position or level an entity holds within a particular formation or organized group.
- F. None of above.
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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a365c92c4cc8190a6b551705c3d66a6 |
completed | June 20, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:45 a.m.