Triple
T37927460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professor Membrane |
E946129
|
entity |
| Predicate | relationshipToGaz |
P204479
|
FINISHED |
| Object | father |
—
|
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: father | Statement: [Professor Membrane, relationshipToGaz, father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToGaz Context triple: [Professor Membrane, relationshipToGaz, father]
-
A.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
B.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
C.
relationshipToGatewayInc
Indicates the nature or type of connection an entity has with Gateway Inc, such as affiliation, ownership, partnership, or other defined relationship.
-
D.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
E.
relationshipToRa
Indicates a specified type of relational connection that an entity has to the entity Ra.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:20 p.m.