Triple
T7580049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Bisayan |
E179461
|
entity |
| Predicate | notAttestedInWriting |
P18534
|
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: [Proto-Bisayan, notAttestedInWriting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAttestedInWriting Context triple: [Proto-Bisayan, notAttestedInWriting, true]
-
A.
attestedInWriting
Indicates that the relationship or fact is documented or confirmed in written form, such as in texts, records, or inscriptions.
-
B.
neverRepudiated
Indicates that an entity has not denied, rejected, or disavowed a previously made statement, action, or association at any point in time.
-
C.
notRecitedOn
Indicates that a particular text, prayer, or recitation was not performed or spoken on a specified occasion, time, or context.
-
D.
isPoorlyAttested
chosen
Indicates that there is limited, weak, or unreliable evidence or documentation supporting the existence, usage, or occurrence of the related item or relationship.
-
E.
attestedBy
Indicates that the existence, occurrence, or validity of something is supported, confirmed, or documented by a specified source or authority.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f975bbc08190aec30f902eaea494 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:52 p.m.