Triple
T8918387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ext3 |
E212349
|
entity |
| Predicate | hasJournalingMode |
P12713
|
FINISHED |
| Object | data=ordered |
—
|
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: data=ordered | Statement: [ext3, hasJournalingMode, data=ordered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJournalingMode Context triple: [ext3, hasJournalingMode, data=ordered]
-
A.
supportsJournalChecksumming
Indicates that an entity provides functionality to compute and verify checksums for journal data to ensure its integrity.
-
B.
hasCompatibilityMode
Indicates that one entity operates under a special mode or setting designed to maintain compatibility with another entity or with an earlier version.
-
C.
hasWorkingMode
chosen
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
D.
hasWritingHistory
Indicates that an entity has a recorded history or log of its writing-related actions, changes, or authored content over time.
-
E.
hasJCR
Indicates that one entity possesses, is associated with, or is linked to a specific JCR (Journal Citation Reports) value, record, or classification.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66120eb08190913ab6c42f26ffb8 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.