Triple
T20985969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La. App. |
E516891
|
entity |
| Predicate | hasAbbreviationForPluralDecisions |
P63320
|
FINISHED |
| Object | La. App. |
—
|
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: La. App. | Statement: [La. App., hasAbbreviationForPluralDecisions, La. App.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbbreviationForPluralDecisions Context triple: [La. App., hasAbbreviationForPluralDecisions, La. App.]
-
A.
hasPluralForm
Indicates that one term is the plural grammatical form of another term.
-
B.
hasPlurality
Indicates that an entity or concept exists or is expressed in a plural form rather than a singular one.
-
C.
hasAbbreviationStatus
Indicates that an entity has a particular status or condition regarding its abbreviation (e.g., whether it is abbreviated, how, or to what extent).
-
D.
usesAbbreviationIn
chosen
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
-
E.
hasAbbreviationOrForm
Indicates that one entity serves as an abbreviation, shortened form, or alternative written form of another entity.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe31cec8190a1007414148b8abe |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.