Triple
T36885299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortescue Group |
E911591
|
entity |
| Predicate | partOfSupergroup |
P203168
|
FINISHED |
| Object | Fortescue Basin succession |
—
|
NE NERFINISHED |
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: Fortescue Basin succession | Statement: [Fortescue Group, partOfSupergroup, Fortescue Basin succession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfSupergroup Context triple: [Fortescue Group, partOfSupergroup, Fortescue Basin succession]
-
A.
supergroupFrom
Indicates that one musical group is a supergroup formed from the members or components of another group.
-
B.
hasSupergroup
Indicates that an entity belongs to or is a member of a larger, encompassing group or category.
-
C.
formedSupergroupWith
Indicates that two or more existing musical acts or groups combined their members to create a new collaborative “supergroup.”
-
D.
supergroupName
Indicates that one entity is the name of a larger group or category (a supergroup) to which another entity belongs.
-
E.
isSupergroupOf
Indicates that one group contains another group as a proper subgroup, having strictly more members or elements than the other.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01302a80ec8190a27692f09ac38a80 |
completed | May 11, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_6a012fad62308190a53f8b4a071eb245 |
completed | May 11, 2026, 1:23 a.m. |
| PDg | Predicate description generation | batch_6a013029b3a48190884d661f6c622cad |
completed | May 11, 2026, 1:26 a.m. |
Created at: May 3, 2026, 4:13 p.m.