Triple
T24912440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giacomo Sumner |
E623881
|
entity |
| Predicate | hasFamilyPublicProfile |
P161425
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Giacomo Sumner, hasFamilyPublicProfile, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyPublicProfile Context triple: [Giacomo Sumner, hasFamilyPublicProfile, true]
-
A.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
B.
hasNationalProfile
Indicates that an entity possesses recognition, presence, or influence at the level of an entire nation rather than being limited to a local or regional scope.
-
C.
hasFamilyFriend
Indicates that one entity has another entity as a friend who is connected through family ties or close familial relationships.
-
D.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
E.
hasCommercialProfile
Indicates that an entity possesses or is associated with a commercial-oriented profile, typically used for business or trade-related purposes.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 18, 2026, 5:28 a.m.