Triple
T35507193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uschi |
E1026181
|
entity |
| Predicate | isTypicallyAssignedTo |
P183381
|
FINISHED |
| Object | girls |
—
|
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: girls | Statement: [Uschi, isTypicallyAssignedTo, girls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyAssignedTo Context triple: [Uschi, isTypicallyAssignedTo, girls]
-
A.
isTypicallyAssignedAt
Indicates that something is most commonly or customarily designated, allocated, or given at a particular time, place, or context.
-
B.
canBeAssignedTo
Indicates that one entity is eligible or permitted to be allocated, designated, or linked to another entity for a particular purpose or role.
-
C.
traditionallyAssignedTo
Indicates that something is customarily or historically designated as the responsibility, role, or domain of a particular entity according to tradition.
-
D.
isTypicallyGrantedTo
Indicates that something is customarily or usually given, awarded, or allowed to a particular recipient or group.
-
E.
assignedInStandard
Indicates that something is allocated or designated within a defined standard, specification, or normative framework.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.