Triple
T10575129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-casual |
E249589
|
entity |
| Predicate | personType |
P94712
|
FINISHED |
| Object | single-person |
—
|
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: single-person | Statement: [T-casual, personType, single-person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personType Context triple: [T-casual, personType, single-person]
-
A.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
B.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
C.
primaryUserType
Indicates the main or dominant category of user associated with an entity or interaction.
-
D.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
E.
namedPartyType
Indicates the specific role or category that a referenced party holds within a given context or 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5274b100c8190b477ef4cb745c269 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:38 p.m.