Triple
T364451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jobs |
E7927
|
entity |
| Predicate | orthographicProperty |
P12752
|
FINISHED |
| Object | beginsWithCapitalJ |
—
|
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: beginsWithCapitalJ | Statement: [Jobs, orthographicProperty, beginsWithCapitalJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orthographicProperty Context triple: [Jobs, orthographicProperty, beginsWithCapitalJ]
-
A.
hasOrthographicPreference
Indicates that one entity prefers or selects a particular written or spelling form of another entity.
-
B.
hasOrthographicReform
Indicates that an entity has undergone or is associated with a change or standardization in its writing system or spelling conventions.
-
C.
hasOfficialOrthography
Indicates that an entity has a formally recognized and standardized system for writing its language or name.
-
D.
hasStandardOrthographySince
Indicates that a language or writing system has used a particular standardized orthography starting from a specified point in time.
-
E.
hasWritingDirection
Indicates the direction in which writing or text is read or written for a given script, language, or text system.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe6c1b4819083335e880c205ed6 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95dbb208190b277fc5352a4ee84 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2eafc8da88190b4a05182f4384442 |
completed | Feb. 28, 2026, 1:17 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.