Triple
T11309931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 摂南大学 |
E267809
|
entity |
| Predicate | 関連法人 |
P629
|
FINISHED |
| Object | 学校法人常翔学園 |
—
|
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: 学校法人常翔学園 | Statement: [摂南大学, 関連法人, 学校法人常翔学園]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 関連法人 Context triple: [摂南大学, 関連法人, 学校法人常翔学園]
-
A.
organizationAssociatedWith
chosen
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
-
B.
hostsOrganizationRelevantToRelations
Indicates that a host entity is associated with an organization that is pertinent or significant to the relationships or interactions being modeled.
-
C.
representativeOrganization
Indicates that one organization acts on behalf of, or serves as the official representative of, another entity in some capacity.
-
D.
associatedCompanyGlobalScope
Indicates that there is a relationship linking an entity to a company at a global (worldwide) organizational scope.
-
E.
memberCompany
Indicates that a company is formally part of, or affiliated as a member with, a larger organization, group, or association.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c0b3b88190ac0e3d6a5ad3b9bc |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.