Triple
T4761112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdon |
E105699
|
entity |
| Predicate | hasFamilyCharacteristic |
P38488
|
FINISHED |
| Object | large family |
—
|
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: large family | Statement: [Abdon, hasFamilyCharacteristic, large family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyCharacteristic Context triple: [Abdon, hasFamilyCharacteristic, large family]
-
A.
familyCharacteristic
chosen
Indicates that a particular trait, feature, or quality is shared within or typical of members of the same family.
-
B.
hasFamilialForm
Indicates that one entity has a version, variant, or form that is specifically used in familial or family-related contexts in relation to another entity.
-
C.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
D.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
E.
hasRepresentativeFamily
Indicates that an entity is associated with a particular family that serves as its representative or characteristic example.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.