Triple
T11671389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Fool's Alphabet |
E277387
|
entity |
| Predicate | hasCentralRelationship |
P24749
|
FINISHED |
| Object | Pietro and his parents |
—
|
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: Pietro and his parents | Statement: [A Fool's Alphabet, hasCentralRelationship, Pietro and his parents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralRelationship Context triple: [A Fool's Alphabet, hasCentralRelationship, Pietro and his parents]
-
A.
hasCentralRelationshipType
chosen
Indicates that there exists a primary or most significant type of relationship that characterizes how two entities are related to each other.
-
B.
hasCentralFamily
Indicates that an entity possesses or is organized around a primary or core family unit.
-
C.
hasCentralAct
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
-
D.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
E.
hasCentralClaim
Indicates that one entity presents or embodies the main assertion, thesis, or primary point made by 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a44264c08190ba1a4a5bcdc9367b |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.