Triple
T33822207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan |
E866857
|
entity |
| Predicate | writtenWithInitialCapital |
P62127
|
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: [Jan, writtenWithInitialCapital, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenWithInitialCapital Context triple: [Jan, writtenWithInitialCapital, true]
-
A.
isWrittenWithInternalCapital
Indicates that a word or phrase is written with at least one capital letter occurring within it, not just at the initial position.
-
B.
capitalizedOn
Indicates that one entity took advantage of, exploited, or made beneficial use of an opportunity, situation, or resource provided or created by another entity.
-
C.
precededByCapital
Indicates that the referenced element is immediately preceded by a capital letter.
-
D.
isCapitalised
chosen
Indicates that a given string or word is written with its first letter in uppercase (and the rest in lowercase, if applicable).
-
E.
capitalizationOccursWhen
Indicates that the event or condition specified is the point or circumstance under which capitalization (e.g., converting letters to uppercase or treating something as a capital asset) takes place.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fffd58008190b8a5cdf852904b59 |
completed | May 3, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.