Triple
T3362616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richie Gecko |
E70758
|
entity |
| Predicate | relativeTypeToSethGecko |
P43530
|
FINISHED |
| Object | younger brother |
—
|
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: younger brother | Statement: [Richie Gecko, relativeTypeToSethGecko, younger brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeTypeToSethGecko Context triple: [Richie Gecko, relativeTypeToSethGecko, younger brother]
-
A.
relatedType
chosen
Indicates that one entity is connected to another through a specified type or category of relationship.
-
B.
relativeMotionType
Indicates the type or nature of motion occurring between two entities relative to one another.
-
C.
oreType
Indicates the specific kind or classification of ore associated with an entity.
-
D.
realmType
Indicates the classification or category of a realm, specifying what kind or type of realm it is.
-
E.
hasStratotype
Indicates that one entity serves as the designated standard or reference example (stratotype) for defining the stratigraphic characteristics of 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb26a5a508190948932769de0dbb3 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.