Triple
T17152070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 勇 |
E416244
|
entity |
| Predicate | usedByRealPersons |
P1480
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [勇, usedByRealPersons, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByRealPersons Context triple: [勇, usedByRealPersons, true]
-
A.
basedOnRealPersonFor
Indicates that one entity is created, modeled, or inspired using a specific real person as its basis.
-
B.
usedByPerson
chosen
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
-
C.
realPerson
Indicates that the referenced entity corresponds to an actual human individual, as opposed to a fictional, anonymous, or non-human entity.
-
D.
basedOnRealLocation
Indicates that something is derived from, inspired by, or modeled after an actual geographic place in the real world.
-
E.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f40861e08190bad1a3ec87691132 |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.