Triple
T36436194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disputation XXIV |
E897589
|
entity |
| Predicate | hasCanonicalAuthorNameForm |
P19207
|
FINISHED |
| Object | Franciscus Suárez |
—
|
NE NERFINISHED |
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: Franciscus Suárez | Statement: [Disputation XXIV, hasCanonicalAuthorNameForm, Franciscus Suárez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalAuthorNameForm Context triple: [Disputation XXIV, hasCanonicalAuthorNameForm, Franciscus Suárez]
-
A.
hasCanonicalNameForm
chosen
Indicates that an entity is associated with its standard or officially recognized name form.
-
B.
hasAuthorGivenNames
Indicates that an entity is associated with the given (first and middle) name or names of its author.
-
C.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
-
D.
hasAuthorRealName
Indicates that an entity (such as a work or pseudonym) is associated with the actual, legal name of its author.
-
E.
isCanonical
Indicates that something represents the standard, authoritative, or officially accepted form within a given context or system.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
Created at: May 3, 2026, 4:10 p.m.