Triple
T18834469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nic |
E460621
|
entity |
| Predicate | relationshipToLaser |
P113623
|
FINISHED |
| Object | mother |
—
|
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: mother | Statement: [Nic, relationshipToLaser, mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToLaser Context triple: [Nic, relationshipToLaser, mother]
-
A.
meetsInRelationTo
Indicates that two or more entities come together or interact within the context of a specified relationship or circumstance.
-
B.
relationshipWithAxis
Indicates a specified way in which something is oriented, aligned, or otherwise related with respect to a particular axis.
-
C.
relationshipToMouse
Indicates the type of relationship or association an entity has with a mouse.
-
D.
relatedToDevice
chosen
Indicates that there exists a general association or connection between an entity and a device, without specifying the exact nature of that relationship.
-
E.
angleRelation
Indicates a relationship specifying how two or more angles are related to each other, such as being equal, complementary, supplementary, or otherwise geometrically constrained.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99c1394819095c62eef040e552c |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.