Triple
T2081703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austronesian alignment |
E45257
|
entity |
| Predicate | marksOn |
P35665
|
FINISHED |
| Object | verb |
—
|
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: verb | Statement: [Austronesian alignment, marksOn, verb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksOn Context triple: [Austronesian alignment, marksOn, verb]
-
A.
marks
Indicates that one entity makes a visible or symbolic sign on, or designates, another entity for identification, emphasis, or distinction.
-
B.
reportedMarks
Indicates that an entity has formally communicated or submitted the marks/grades of another entity (such as a student or assessment) to a relevant party or system.
-
C.
markType
Indicates the specific category or kind of mark associated with or applied to an entity.
-
D.
mintMarkUsedOn
Indicates that a particular mint mark was applied to or appears on a specific coin or numismatic item.
-
E.
marksOccasion
Indicates that an event, action, or item serves to commemorate, celebrate, or formally recognize a particular occasion or milestone.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba35c2588190933dba882f52dd17 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:41 p.m.