Triple
T28219305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G. Simmons |
E711405
|
entity |
| Predicate | namingConnectionType |
P164133
|
FINISHED |
| Object | familial or commemorative naming connection |
—
|
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: familial or commemorative naming connection | Statement: [G. Simmons, namingConnectionType, familial or commemorative naming connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingConnectionType Context triple: [G. Simmons, namingConnectionType, familial or commemorative naming connection]
-
A.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
B.
commonConnectorName
Indicates that two or more entities share the same connector name used to link or interface them.
-
C.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
D.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
E.
connectionEstablishmentMethod
Indicates the method or mechanism by which a connection between entities is initiated or established.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6434f9f888190bd43fde92cd729fe |
completed | May 2, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:45 p.m.