Triple
T11008119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jade |
E260173
|
entity |
| Predicate | relationshipTypeWithStuPrice |
P96982
|
FINISHED |
| Object | brief wife |
—
|
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: brief wife | Statement: [Jade, relationshipTypeWithStuPrice, brief wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithStuPrice Context triple: [Jade, relationshipTypeWithStuPrice, brief wife]
-
A.
tuitionFeeType
Indicates the category or structure of tuition fees that applies to an entity (such as full-time, part-time, in-state, out-of-state, or other fee types).
-
B.
enrollmentType
Indicates the specific category or mode under which an entity is enrolled in a program, service, or system.
-
C.
relationshipToUniversity
Indicates the type or nature of a person's or entity's connection or affiliation with a specific university.
-
D.
hasStudentCategory
Indicates that an entity is classified under a specific category or type of student.
-
E.
associatedWithSchool
Indicates a relationship where an entity has a connection or affiliation with a particular school, such as attendance, employment, or partnership.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79757bdcc8190900b267826eece21 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d733b27ffc81908ab1b8df198cd5c7 |
completed | April 9, 2026, 5:05 a.m. |
Created at: April 8, 2026, 9:25 p.m.