Triple
T7219869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladas |
E150228
|
entity |
| Predicate | enteredStud |
P75521
|
FINISHED |
| Object | late 1890s |
—
|
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: late 1890s | Statement: [Ladas, enteredStud, late 1890s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredStud Context triple: [Ladas, enteredStud, late 1890s]
-
A.
stoodAtStudAt
Indicates that one entity was positioned or located at a particular stud (e.g., structural post or support point).
-
B.
hasStudentEnrollment
Indicates that a person or entity is enrolled as a student in a particular course, program, or educational institution.
-
C.
standingAtStud
Indicates that one entity is standing at or positioned next to a specific stud or stud-like structural element.
-
D.
isStudiedIn
Indicates that a subject (such as a topic, field, or phenomenon) is examined, researched, or learned about within a particular context, environment, or discipline.
-
E.
enrollment
Indicates the formal act of registering or being registered in a course, program, or institution, establishing an official participant–provider relationship.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b1a7908190bd215ffb84592e32 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:53 p.m.