Triple
T10357594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarō |
E244039
|
entity |
| Predicate | isCommonFor |
P32595
|
FINISHED |
| Object | males |
—
|
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: males | Statement: [Tarō, isCommonFor, males]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonFor Context triple: [Tarō, isCommonFor, males]
-
A.
commonFor
chosen
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
-
B.
isCommonlyDefinedBy
Indicates that something is typically or most frequently characterized, specified, or described by a particular definition, property, or set of criteria.
-
C.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
D.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
E.
hasCommonSpace
Indicates that two or more entities share access to the same physical or virtual area intended for joint or overlapping use.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9563ea48190b8702b3ef497ed9a |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:58 a.m.