Triple
T37491933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robin Gamgee |
E931712
|
entity |
| Predicate | belongsToFamilyLine |
P4276
|
FINISHED |
| Object | Gamgee–Gardner family |
—
|
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: Gamgee–Gardner family | Statement: [Robin Gamgee, belongsToFamilyLine, Gamgee–Gardner family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToFamilyLine Context triple: [Robin Gamgee, belongsToFamilyLine, Gamgee–Gardner family]
-
A.
belongsToFamily
chosen
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
B.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
-
C.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
D.
hasOrdinalInFamilyLine
Indicates that an entity holds a specific ordinal position (e.g., first, second, third) within a family lineage or sequence of family members.
-
E.
belongsToLegalFamily
Indicates that one entity is a member of, or is legally affiliated with, a particular legal family or legal system tradition.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
Created at: May 3, 2026, 4:17 p.m.